Method and apparatus for setting or modifying programmable parameter in power driven wheelchair

ABSTRACT

A method and apparatus for setting or modifying a programmable operating parameter associated with a power driven wheelchair is provided. In one embodiment, the method includes: a) operating a user interface device associated with a power driven wheelchair in a programming mode, b) selecting a programmable operating parameter associated with operation of the power driven wheelchair using the user interface device, c) selecting a value for the programmable operating parameter using the user interface device, and d) saving the selected value for the programmable operating parameter in a portion of a storage device associated with the power driven wheelchair using the user interface device. A method and apparatus for selecting one or more programmable parameter sets from a portable storage medium and saving the selected sets to a local storage device associated with a power driven wheelchair and vice versa is also provided.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/381,649, filed on Dec. 16, 2016, now U.S. Pat. No. 10,130,534, whichis a continuation of U.S. patent application Ser. No. 14/802,221, filedon Jul. 17, 2015, now U.S. Pat. No. 9,522,091, which is a continuationof U.S. patent application Ser. No. 13/975,614, filed on Aug. 26, 2013,now U.S. Pat. No. 9,084,705, which is a continuation of U.S. patentapplication Ser. No. 13/646,989, filed on Oct. 8, 2012, now abandoned,which is a continuation of U.S. patent application Ser. No. 13/228,677,filed on Sep. 9, 2011, now U.S. Pat. No. 8,285,440, which is adivisional of U.S. patent application Ser. No. 11/513,750, filed on Aug.31, 2006, now U.S. Pat. No. 8,073,585, which claims the benefit of eightU.S. provisional patent applications, including Ser. No. 60/712,987,filed Aug. 31, 2005, Ser. No. 60/727,005, filed Oct. 15, 2005, Ser. No.60/726,983, filed Oct. 15, 2005, Ser. No. 60/726,666, filed Oct. 15,2005, Ser. No. 60/726,981, filed Oct. 15, 2005, Ser. No. 60/726,993,filed Oct. 15, 2005, Ser. No. 60/727,249, filed Oct. 15, 2005, and Ser.No. 60/727,250, filed Oct. 15, 2005. This application is also related toseven non-provisional U.S. patent applications filed on the same day,including Ser. No. 11/513,740, now abandoned, entitled “ModeProgrammable Actuator Controller for Power Positioning Seat or LegSupport of a Wheelchair,” Ser. No. 11/514,016, now U.S. Pat. No.8,073,588, entitled “Method and Apparatus for Setting or ModifyingProgrammable Parameters in Power Driven Wheelchair,” Ser. No.11/511,606, now U.S. Pat. No. 7,403,844, entitled “Method and Apparatusfor Programming Parameters of a Power Driven Wheelchair for a Pluralityof Drive Settings,” Ser. No. 11/513,780, now abandoned, entitled“Adjustable Mount for Controller of Power Driven Wheelchair,” Ser. No.11/513,746, now abandoned, entitled “Method and Apparatus for AutomatedPositioning of User Support Surfaces in Power Driven Wheelchair,” Ser.No. 11/513,854, now U.S. Pat. No. 8,065,051, entitled “Context-SensitiveHelp for Display Device Associated with a Power Driven Wheelchair,” andSer. No. 11/513,802, now U.S. Pat. No. 8,127,875, entitled “Power DrivenWheelchair.” The contents of all above-identified patent application(s)and patent(s) are fully incorporated herein by reference.

BACKGROUND

Power driven wheelchairs generally include right and left drive wheelsdriven by a motor controller via corresponding right and left drivemotors. A power driven wheelchair may also include actuators, motors, orother devices to control user support surfaces, such as seats, backs,leg rests, foot rests, or head rests. These various actuators, motors,and other devices may be controlled via a user interface device. Theuser interface device may include input devices, such as a joystick,pushbuttons and other types of switches, potentiometers and other typesof control devices, and output devices, such as a graphic display,alphanumeric display, or indicators. Input devices for special needsusers, such as a proportional head control, a sip n′ puff system, afiber optic tray array, a proximity head array, or a proximity switcharray, may also be provided as a user interface device or as a remoteinput to the user interface device.

Examples of power driven wheelchairs are provided in a product brochureentitled “Invacare® Storm® Series TDX™ Power Wheelchairs, includingFormula™ Powered Seating,” Form No. 03-018, 2004 from InvacareCorporation of Elyria, Ohio, the contents of which are fullyincorporated herein by reference. Additional examples of power drivenwheelchairs are provided in another product brochure entitled “Invacare®Tarsys® Series Powered Seating System,” Form No. 00-313, 2002 fromInvacare Corporation, the contents of which are fully incorporatedherein by reference.

Currently, a separate remote programmer unit may be used to set ormodify programmable parameters associated with operation of a givenpower driven wheelchair. Examples of remote programmers and their use inconjunction with a power driven wheelchair are provided in U.S. Pat. No.6,871,122 to Wakefield, II and U.S. Pat. No. 6,819,981 to Wakefield, IIet al., both assigned to Invacare Corporation. The contents of both ofthese patents are fully incorporated herein by reference.\

SUMMARY

In one aspect an apparatus associated with a power driven wheelchair forsetting or modifying a programmable parameter is provided. In oneembodiment, the apparatus includes: a user interface device associatedwith a power driven wheelchair and adapted to operate in a programmingmode and a first storage device in operative communication with the userinterface device with at least a portion designated for storage of aprogrammable operating parameter associated with operation of the powerdriven wheelchair. In this embodiment, the user interface device is usedto select the programmable operating parameter, select a value for theprogrammable operating parameter, and save the selected value for theprogrammable operating parameter in the portion of the first storagedevice.

In another aspect, a method associated with a power driven wheelchairfor setting or modifying a programmable parameter is provided. In oneembodiment, the method includes: a) operating a user interface deviceassociated with a power driven wheelchair in a programming mode, b)selecting a programmable operating parameter associated with operationof the power driven wheelchair using the user interface device, c)selecting a value for the programmable operating parameter using theuser interface device, and d) saving the selected value for theprogrammable operating parameter in a portion of a storage deviceassociated with the power driven wheelchair using the user interfacedevice.

In still another aspect, an apparatus associated with a power drivenwheelchair for communicating a programmable parameter set is provided.In one embodiment, the apparatus includes: a user interface deviceassociated with a power driven wheelchair and adapted to operate in aprogramming mode, a portable storage medium in operative communicationwith the user interface device with at least a portion designated forstorage of one or more programmable parameter sets associated withoperation of the power driven wheelchair, and a local storage device inoperative communication with the user interface device with at least aportion designated for storage of one or more programmable parametersets associated with operation of the power driven wheelchair. In thisembodiment, the user interface device is used to select one or moreprogrammable parameter sets from the portable storage medium and savesaid selected programmable parameter sets to the local storage device orvice versa.

In yet another aspect, a method associated with a power drivenwheelchair for communicating a programmable parameter set is provided.In one embodiment, the method includes: a) operating a user interfacedevice associated with a power driven wheelchair in a programming mode,b) selecting at least one programmable parameter set associated with thepower driven wheelchair using the user interface device, and c)communicating each selected programmable parameter set from a portablestorage medium associated with the power driven wheelchair to a localstorage device associated with the power driven wheelchair or vice versausing the user interface device. In this embodiment, the portablestorage device includes at least a portion designated for storage of oneor more programmable parameter sets and the local storage deviceincludes at least a portion designated for storage of one or moreprogrammable parameter sets.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1 and 2 show exemplary embodiments of power driven wheelchairs.

FIG. 3 is a block diagram of an exemplary embodiment of a power drivenwheelchair.

FIG. 4 is a block diagram of an exemplary embodiment of a systemcontroller for a power driven wheelchair.

FIG. 5 is a block diagram of an exemplary embodiment of a programmerused in conjunction with related embodiments of power drivenwheelchairs.

FIG. 6 is a block diagram of an exemplary embodiment of a local storagedevice associated with a system controller.

FIG. 7 is a block diagram of an exemplary embodiment of a portablestorage medium associated with a system controller or a programmer.

FIGS. 8 through 11 are perspective views of exemplary embodiments of asystem controller for a power driven wheelchair.

FIG. 12 is a perspective view of an exemplary embodiment of a programmerused in conjunction with related embodiments of power drivenwheelchairs.

FIGS. 13 and 14 are examples of sequences of display screens associatedwith setting or modifying an exemplary programmable parameter within aselected programmable parameter set associated with a power drivenwheelchair.

FIG. 15 is an exemplary menu hierarchy for a programming mode associatedwith operation or support of a power driven wheelchair.

FIG. 16 is a flow chart of an exemplary mode select monitor processassociated with setting or modifying a programmable parameter.

FIG. 17 is a flow chart of an exemplary programming process associatedwith setting or modifying a programmable parameter.

FIG. 18 is a flow chart of an exemplary menu navigation sub-processassociated with setting or modifying a programmable parameter.

FIG. 19 is a flow chart of an exemplary menu item selection handlersub-process associated with setting or modifying a programmableparameter.

FIG. 20 is a flow chart of an exemplary set/modify parameter handlersub-process associated with setting or modifying a programmableparameter.

FIG. 21 is a flow chart of an exemplary drive select monitor sub-processassociated with setting or modifying a programmable parameter.

FIGS. 22 and 23 are examples of sequences of display screens on anapparatus associated with a power driven wheelchair for communicatingone or more library parameter sets from a portable storage medium to alocal storage device associated with the power driven wheelchair.

FIGS. 24 and 25 are examples of sequences of display screens on anapparatus associated with a power driven wheelchair for communicatingone or more programmable parameter sets from a local storage deviceassociated with the power driven wheelchair to a portable storagemedium.

FIG. 26 is an exemplary block diagram of an apparatus associated with apower driven wheelchair for setting or modifying a programmableparameter.

FIG. 27 is an exemplary flow chart of a process associated with a powerdriven wheelchair for setting or modifying a programmable parameter.

FIG. 28 is an exemplary block diagram of an apparatus associated with apower driven wheelchair for communicating a programmable parameter set.

FIG. 29 is an exemplary flow chart of a process associated with a powerdriven wheelchair for communicating a programmable parameter set.

DETAILED DESCRIPTION

The following paragraphs include definitions of exemplary terms usedwithin this disclosure. Except where noted otherwise, variants of allterms, including singular forms, plural forms, and other affixed forms,fall within each exemplary term meaning. Except where noted otherwise,capitalized and non-capitalized forms of all terms fall within eachmeaning.

“Circuit,” as used herein includes, but is not limited to, hardware,firmware, software or combinations of each to perform a function(s) oran action(s). For example, based on a desired feature or need, a circuitmay include a software controlled microprocessor, discrete logic such asan application specific integrated circuit (ASIC), or other programmedlogic device. A circuit may also be fully embodied as software. As usedherein, “circuit” is considered synonymous with “logic.”

“Comprising,” “containing,” “having,” and “including,” as used herein,except where noted otherwise, are synonymous and open-ended. In otherwords, usage of any of these terms (or variants thereof) does notexclude one or more additional elements or method steps from being addedin combination with one or more enumerated elements or method steps.

“Controller,” as used herein includes, but is not limited to, anycircuit or device that coordinates and controls the operation of one ormore input or output devices. For example, a controller can include adevice having one or more processors, microprocessors, or centralprocessing units (CPUs) capable of being programmed to perform input oroutput functions.

“Logic,” as used herein includes, but is not limited to, hardware,firmware, software or combinations of each to perform a function(s) oran action(s), or to cause a function or action from another component.For example, based on a desired application or need, logic may include asoftware controlled microprocessor, discrete logic such as anapplication specific integrated circuit (ASIC), or other programmedlogic device. Logic may also be fully embodied as software. As usedherein, “logic” is considered synonymous with “circuit.”

“Operative communication,” as used herein includes, but is not limitedto, a communicative relationship between devices, logic, or circuits,including mechanical and pneumatic relationships. Direct electrical,electromagnetic, and optical connections and indirect electrical,electromagnetic, and optical connections are examples of suchcommunications. Linkages, gears, chains, push rods, cams, keys,attaching hardware, and other components facilitating mechanicalconnections are also examples of such communications. Pneumatic devicesand interconnecting pneumatic tubing may also contribute to operativecommunications. Two devices are in operative communication if an actionfrom one causes an effect in the other, regardless of whether the actionis modified by some other device. For example, two devices separated byone or more of the following: i) amplifiers, ii) filters, iii)transformers, iv) optical isolators, v) digital or analog buffers, vi)analog integrators, vii) other electronic circuitry, viii) fiber optictransceivers, ix) Bluetooth communications links, x) 802.11communications links, xi) satellite communication links, and xii) otherwireless communication links. As another example, an electromagneticsensor is in operative communication with a signal if it receiveselectromagnetic radiation from the signal. As a final example, twodevices not directly connected to each other, but both capable ofinterfacing with a third device, e.g., a central processing unit (CPU),are in operative communication.

“Or,” as used herein, except where noted otherwise, is inclusive, ratherthan exclusive. In other words, “or” is used to describe a list ofalternative things in which one may choose one option or any combinationof alternative options. For example, “A or B” means “A or B or both” and“A, B, or C” means “A, B, or C, in any combination.” If “or” is used toindicate an exclusive choice of alternatives or if there is anylimitation on combinations of alternatives, the list of alternativesspecifically indicates that choices are exclusive or that certaincombinations are not included. For example, “A or B, but not both” isused to indicate use of an exclusive “or” condition. Similarly, “A, B,or C, but no combinations” and “A, B, or C, but not the combination ofA, B, and C” are examples where certain combination of alternatives arenot included in the choices associated with the list.

“Processor,” as used herein includes, but is not limited to, one or moreof virtually any number of processor systems or stand-alone processors,such as microprocessors, microcontrollers, central processing units(CPUs), and digital signal processors (DSPs), in any combination. Theprocessor may be associated with various other circuits that supportoperation of the processor, such as random access memory (RAM),read-only memory (ROM), programmable read-only memory (PROM), erasableprogrammable read-only memory (EPROM), clocks, decoders, memorycontrollers, or interrupt controllers, etc. These support circuits maybe internal or external to the processor or its associated electronicpackaging. The support circuits are in operative communication with theprocessor. The support circuits are not necessarily shown separate fromthe processor in block diagrams or other drawings.

“Signal,” as used herein includes, but is not limited to, one or moreelectrical signals, including analog or digital signals, one or morecomputer instructions, a bit or bit stream, or the like.

“Software,” as used herein includes, but is not limited to, one or morecomputer readable or executable instructions that cause a computer orother electronic device to perform functions, actions, or behave in adesired manner. The instructions may be embodied in various forms suchas routines, algorithms, modules or programs including separateapplications or code from dynamically linked libraries. Software mayalso be implemented in various forms such as a stand-alone program, afunction call, a servlet, an applet, instructions stored in a memory,part of an operating system, or other types of executable instructions.It will be appreciated by one of ordinary skill in the art that the formof software is dependent on, for example, requirements of a desiredapplication, the environment it runs on, or the desires of adesigner/programmer or the like.

With reference to FIG. 1, an exemplary embodiment of a power drivenwheelchair 10 includes a system controller 12. The system controller 12controls operation of the power driven wheelchair 10. Other embodimentsof power driven wheelchairs and other embodiments of system controllersare available in various combinations. For example, as shown if FIG. 2,another exemplary embodiment of a power driven wheelchair 20 includes asystem controller 22.

With reference to FIG. 3, an exemplary embodiment of a power drivenwheelchair 30 is depicted in block diagram fashion. As shown, the powerdriven wheelchair 30 may include a system controller 32, a drivecontroller 34, a left drive motor 36, a right drive motor 38, and asuitable power source (e.g., battery) (not shown). The system controller32 may include a user interface device and may control the drivecontroller 34 in response to activation of one or more input devicesassociated with the user interface device and in response to softwareprograms for one or more operating or support modes. The softwareprograms may use a plurality of programmable parameters arranged in setsassociated with, for example, different environmental conditions todefine driving response characteristics. The drive controller 34 maycontrol the left and right drive motors 36, 38 in response to commandsfrom the system controller 32. Communication between the systemcontroller 32 and drive controller 34 may be via serial or parallel busconnections or via discrete signal connections. For example, a Sharkserial communication bus, developed by Dynamic Controls of New Zealand,may be used to communicate with the drive controller 34. In anotherembodiment, the system controller 34 may communicate directly with aleft drive motor and a right drive motor via a serial communication bus,such as a controller area network (CAN) bus, where the left and rightdrive motors include a serial bus interface and local intelligence.

The power driven wheelchair 30 may also include various options, such aspowered seating, powered front rigging, and powered steering. In oneembodiment, the powered seating option may include a tilt actuator 40, arecline actuator 42, an elevation actuator 44, a horizontal actuator 46,and a ventilator tray actuator 48. In one embodiment, the powered frontrigging option may include a common leg rest actuator 50 and a commonfoot rest actuator 52. In another embodiment, the powered front riggingoption may include independent left and right leg rest actuators andindependent left and right foot rest actuators. In one embodiment, thepowered steering option may include one or more powered steeringactuators 54. These options may be added to the wheelchair in anycombination. Likewise, various combinations of actuators may be selectedfor each option. For example, a powered seating option may be limited totilt and recline actuators 40, 42, tilt and elevation actuators 40, 44,recline and elevation actuators 40, 46, or tilt, recline, and elevationactuators 40, 42, 44. If the power driven wheelchair has split left andright leg rests, individual right and left leg rest actuators may beprovided in lieu of the common leg rest actuator 50. Back and seat shearreduction, for example, may be provided by coordinated movement of therecline and horizontal actuators 42, 46. The system controller 32 maycontrol the actuators in response to activation of one or more inputdevices associated with the user interface device and in response tosoftware programs for one or more operating or support modes. Thesoftware programs may use a plurality of programmable parameters, forexample, to define desired positions for user support surfaces andactuator response characteristics. Communication between the systemcontroller 32 and actuators may be via serial or parallel busconnections or via discrete signal connections. For example, in oneembodiment, actuators may include sensors and local electronics whichprovides an interface to a CAN bus. It is understood that any actuatormay include a variable speed reversible motor, a stepper motor, a linearmotor, a servo motor, or another suitable device associated withposition control of an actuator mechanism. The actuator mechanism, forexample, controlling the position of user support surfaces, such asseat, back, leg rest, foot rest, or head rest support surfaces, via asuitable linkage, drive train, coupling, or another type of mechanicalinterface.

In one embodiment, providing modularization of actuators, motors, andother output devices with sensors, detectors, or other devices providingfeedback for closed loop control of the corresponding output devicefacilitates the use of a serial or parallel bus architecture in thepower driven wheelchair 30. This also simplifies the addition or removalof optional output devices and streamlines upgrades and retrofits.Moreover, distributing intelligence, including interface circuits foroutput devices and associated feedback components, from the centralizedcontroller to the modular output devices further improves performancethrough parallel processing. In additional embodiments, distributingadditional intelligence, including closed-loop control algorithms, fromthe centralized controller to the modular output devices furtherimproves performance through additional parallel processing and reducedbus traffic.

One or more remote input devices 58 may also be provided as options inthe power driven wheelchair 30. For example, user interface devices forspecial needs users, such as a proportional head control, a sip n′ puffsystem, a fiber optic tray array, a proximity head array, or a proximityswitch array, may be provided as a remote input to the system controller32. Additional examples of remote input devices 58 include, a 4-waytoggle switch assembly, a quad pushbutton assembly, and a compactproportional joystick assembly. The 4-way toggle switch assembly or thequad pushbutton assembly, for example, may be used for controllingpowered seating systems. The compact proportional joystick assembly, forexample, may be used as a proportional attendant control. Communicationbetween the system controller 32 and the remote input device(s) 58 maybe via serial or parallel bus connections or via discrete signalconnections. For example, a remote input device may be connected to aserial port on the system controller 32. If the remote input deviceincludes the appropriate electronics and local intelligence (e.g.,processes for composing and de-composing bus messages), communicationswith the system controller 32 may, for example, be via a CAN bus oranother type of bus or network connection.

A programmer 60 may be used in conjunction with the power drivenwheelchair 30. The programmer 60 described herein may be an optionalaccessory or special tool for dealers or technicians. The programmer 60may be adapted for use on various models and configurations of powerdriven wheelchairs. Communication between the system controller 32 andthe programmer 60 may be via serial or parallel bus connections or viadiscrete signal connections. For example, the programmer 60 may beconnected to a serial port on the system controller 32. If theprogrammer 60 includes the appropriate electronics and localintelligence (e.g., processes for composing and de-composing busmessages), communications with the system controller 32 may, forexample, be via a CAN bus or another type of bus or network connection.The various aspects of FIG. 3 described above may be automated,semi-automated, or manual and may be implemented through hardware,software, firmware, or combinations thereof.

With reference to FIG. 4, a block diagram of an exemplary embodiment ofa system controller 32 may include a microcontroller 62, one or moreinput devices 64, a display 66, one or more indicators 68, an on-boardstorage device 70, a storage medium interface 72, an output deviceinterface 74, one or more remote input device interfaces 76, and aprogrammer interface 78. The microcontroller 62 may include a centralprocessing unit (CPU) 80, an on-chip storage device 82, and ananalog-to-digital (A/D) converter 84. The A/D converter 84 may providethe microcontroller 62 with an interface to receive analog inputsignals. In one embodiment, the microcontroller 62 may include anSAF-XC164CS 16-bit single-chip microcontroller by Infineon Technologiesof München, Germany.

The display 66, for example, may include a 128×64 pixel graphic displayor a 160×160 pixel graphic display. In additional embodiments, thedisplay may include a graphic display in a different size or a differentarrangement of pixels. Any type of graphic display may be used, such asa liquid crystal display (LCD). Additionally, an alphanumeric display oranother type of display may be used. The one or more indicators 68, forexample, may include light emitting diodes (LEDs), lamps, other types ofvisual indicators, or audible devices. The one or more input devices 64,for example, may include a proportional analog joystick, a threeposition toggle or rotary switch, a return-to-center momentary threeposition switch, a rotary potentiometer, and a plurality of momentarypushbuttons. In additional embodiments, the one or more input devices64, may include other types of joysticks, switches, potentiometers,pushbuttons, or other types of control devices.

The output device interface 74 may be connected, for example, to a motorcontroller, actuators, motors, or similar devices associated with thepower driven wheelchair. The output device interface 74 may include oneor more serial ports, one or more parallel ports, or discrete wiringconnections in any combination. For example, the output device interface74 may include a CAN bus serial port and a Shark bus serial port. Theone or more remote input device interfaces 76 and programmer interface78 may each include a serial port, parallel port, or discrete wiringconnections.

The microcontroller 62 may receive input signals from the one or moreinput devices 64, remote input devices 58 (FIG. 2) connected to the oneor more remote input device interfaces 76, or a programmer 60 (FIG. 2)connected to the programmer interface 78. The microcontroller 62 maycontrol the display 66, the one or more indicators 68, and variousmotors, actuators, and other output devices connected to the outputdevice interface 74, at least in part, in response to the input signalsfrom the one or more input devices 64, remote input devices 58 (FIG. 2),or programmer 60 (FIG. 2).

The on-board storage device 70 and on-chip storage device 82 each mayinclude a volatile storage device, such as random access memory (RAM),and a non-volatile storage device, such as non-volatile memory, a fixeddisk device, a removable disc device, an optical storage device, etc.Non-volatile memory, for example, may include read-only memory (ROM),programmable read-only memory (PROM), erasable programmable read-onlymemory (EPROM), electrically erasable programmable read only memory(EEPROM), or flash memory. For example, software programs, one or moreprogrammable parameter sets, and help information may be stored in oneor more non-volatile memory storage devices associated with the on-boardstorage device 70 or on-chip storage device 82. Each programmableparameter set may include a plurality of programmable operatingparameters for the power driven wheelchair 20. The microcontroller 62may run the software programs and may control the display 66, indicators68, and various motors, actuators, and other output devices connected tothe output device interface 74 based, at least in part, on one or moreof the programmable operating parameters.

A portable storage medium 86 may be used in conjunction with the systemcontroller 32. The portable storage medium 86 may include a plurality ofstorage locations which may store a security key, one or more libraryparameter sets, and a collection of help information. The portablestorage medium 86 described herein may be an optional accessory orspecial tool for dealers or technicians. In some cases, the portablestorage medium 86 may also be used in conjunction with normal operationof the power driven wheelchair by its owner or end user. The portablestorage medium 86 described herein may be suitable for use on variousmodels and configurations of power driven wheelchairs. However, inanother scheme for protection and security of the information storedtherein, a given portable storage medium 86 may be serialized orotherwise tailored and keyed to an individual system controller 32 andcorresponding power driven wheelchair. Communication between themicrocontroller 62 and the portable storage medium 86 may be via thestorage medium interface 72.

The portable storage medium 86 may include a non-volatile storagemedium, such as non-volatile memory. In one embodiment, the portablestorage medium 86 may include, for example, a type of removable storagemedium known as a removable memory card. For example, the portablestorage medium 86 may include a secure digital (SD) card. In theembodiment being described, the storage medium interface 72 may include,for example, a corresponding removable memory interface (e.g., an SDcard reader) to communicate and exchange information with themicrocontroller 62.

In additional embodiments, the portable storage medium may include othertypes of removable memory, such as a compact flash (CF) card, a flashmemory pen drive, a memory stick, a microdrive, a multimedia memory card(MMC), a smart media (SM) card, an xD picture card, a subscriberidentity module (SIM) card, a memory chip (e.g., ROM, PROM, EPROM,EEPROM), or another suitable form of removable, separable, or detachablememory. In other additional embodiments, the portable storage medium mayinclude other forms of removable storage medium, such as optical discs(e.g., compact discs (CDs), digital video discs (DVDs)) or floppy disks(e.g., zip disks).

In still further embodiments, the portable storage medium may include aportable storage device, such as an external memory card reader, anexternal optical disc drive, an external floppy disk drive, a portablecomputer (e.g., laptops, notebooks, personal digital assistants (PDAs)),a mobile telephone (e.g., cellular telephone, personal communicationsystem, satellite telephone), a digital camera, an MP3 player, or anytype of portable storage device capable of wired or wirelesscommunication with another compatible communication device.

The storage medium interface 72, for example, may include a connector orsocket that mates with the portable storage medium 86 and an electroniccircuit that supports communication between the microcontroller 62 andthe portable storage medium 86. For example, the storage mediuminterface 72 may include a memory card reader, a memory chip socket, anoptical disc drive, a floppy disk drive, a serial port (e.g., universalserial bus (USB) port, RS-232), a parallel port (e.g., small computersystem interface (SCSI) port), a modem, an Ethernet port, a wirelessEthernet transceiver (e.g., IEEE 802.11b), a Bluetooth transceiver, aninfrared (IR) transceiver, a radio frequency (RF) transceiver, a mobiletelephone interface, a cable television interface, a satellitetelevision interface, or any communication device capable of wired orwireless communication with a corresponding portable storage medium. Thevarious aspects of FIG. 4 described above may be automated,semi-automated, or manual and may be implemented through hardware,software, firmware, or combinations thereof.

With reference to FIG. 5, an exemplary embodiment of a programmer 60 mayinclude a microcontroller 88, one or more input devices 90, a display92, one or more indicators 94, an on-board storage device 96, a storagemedium interface 98, and a controller interface 100. The microcontroller88 may include a CPU 102 and an on-chip storage device 104. In oneembodiment, the microcontroller 88 may include an SAF-XC164CS 16-bitsingle-chip microcontroller by Infineon Technologies of München,Germany.

The display 92, for example, may include a 160×160 pixel graphicdisplay. In additional embodiments, the display may include a graphicdisplay in a different size or a different arrangement of pixels. Anytype of graphic display may be used, such as an LCD. Additionally, analphanumeric display or another type of display may be used. The one ormore indicators 94, for example, may include LEDs, lamps, other types ofvisual indicators, or audible devices. The one or more input devices 90,for example, may include a plurality of momentary pushbuttons. Inadditional embodiments, the one or more input devices 90, may includeother types of pushbuttons or other types of control devices.

The controller interface 100 may include a serial port, parallel port,or discrete wiring connections for interfacing with a system controller32 (FIG. 2) of a power driven wheelchair. The microcontroller 88 mayreceive input signals from the one or more input devices 90 and thesystem controller connected to the controller interface 100. Themicrocontroller 88 may latch or store activations of the one or moreinput devices 90 or other input signals over time. The microcontroller88 may control the display 92 and the one or more indicators 94, atleast in part, in response to the input signals from the one or moreinput devices or the system controller.

The microcontroller 88 may periodically (e.g., every 10 ms) receive astatus check message from the system controller 32 (FIG. 2) via thecontroller interface 100. For example, if an activation of the one ormore input devices 90 has occurred since the last status check, themicrocontroller 88 may send a response to the status check message viathe controller interface 100 that may include information regarding thelatched or stored activations from the one or more input devices 90.Once the response is sent, certain latched or stored activations may becleared. If no activations occurred since the last status check, themicrocontroller 88 may send a response to the status check messageindicating there is no new data to send. The microcontroller 88, forexample, may also receive messages from system controller via thecontroller interface 100 containing information to be displayed on thedisplay 92 or commands regarding control of the display 92.

The on-board storage device 96 and on-chip storage device 104 each mayinclude a volatile storage device, such as RAM, and a non-volatilestorage device, such as non-volatile memory, a fixed disk device, aremovable disc device, an optical storage device, etc. Non-volatilememory, for example, may include ROM, PROM, EPROM, EEPROM, or flashmemory. For example, software programs, a plurality of programmableparameter sets, and help information may be stored in one or morenon-volatile memory storage devices associated with the on-board storagedevice 96 or on-chip storage device 104. The microcontroller 88 may runthe software programs and may control the display 92 and indicators 94based, at least in part, on one or more of the programmable operatingparameters.

A portable storage medium 106 may be used in conjunction with theprogrammer 60. Like the portable storage medium 86 (FIG. 4) associatedwith the system controller 32 (FIG. 4), the portable storage medium 106may also be an optional accessory or special tool for dealers ortechnicians. Therefore, the various characteristics, options, andalternatives described above for the portable storage medium 86 (FIG. 4)and storage medium interface 72 (FIG. 4) also apply to the portablestorage medium 106 and storage medium interface 98 in the programmer 60.The microcontroller 88 is in communication with the portable storagemedium 106 via the storage medium interface 98. This enables themicrocontroller 88 to retrieve data from the portable storage medium 106and provide it to the system controller via the controller interface 100or to save data received from the system controller to the portablestorage medium 106.

In one embodiment, the portable storage medium 106 associated with theprogrammer 60 and the portable storage medium 86 (FIG. 4) associatedwith the system controller 32 (FIG. 2) may be interchangeable. In otherwords, the portable storage medium 106 may be used in conjunction withthe system controller and vice versa.

Moreover, this interchangeability may extend to other power drivenwheelchairs. In other words, the portable storage medium 86 (FIG. 4) or106 (FIG. 5) associated with the power driven wheelchair 10 (FIG. 1) maybe used in system controllers or programmers associated with other powerdriven wheelchairs. This facilitates development of a master copy oflibrary parameter sets on one or more portable storage medium that canbe transported to multiple power driven wheelchairs for selectivecommunication of library parameter sets from the master copy tocorresponding system controllers associated with each power drivenwheelchair. Additionally, programmable parameter sets can be selectivelyuploaded to the master copy to build or grow the library parameter setsfrom individual power driven wheelchairs. This is particularly usefulafter modifying a selected programmable parameter set on a first powerdriven wheelchair for a first user when a second user with a similarpower driven wheelchair and similar physical impairments is identified.While a library parameter set and a corresponding programmable parameterset are equivalent (i.e., both including the same plurality ofprogrammable operating parameters), it is sometimes useful to use thephrase “library parameter set” to refer to the plurality of programmableoperating parameters on the portable storage medium and to use thephrase “programmable parameter set” to refer to them within the systemcontroller. Nevertheless, the phrases have the same meaning and may beused interchangeably to refer to the plurality of programming operatingparameters in any location. The various aspects of FIG. 5 describedabove may be automated, semi-automated, or manual and may be implementedthrough hardware, software, firmware, or combinations thereof.

With reference to FIG. 6, an exemplary embodiment of a local storagedevice 107 associated with a system controller 32 (FIG. 4) may include aplurality of storage locations that may store software programs 108 anda plurality of programmable parameter sets. The local storage device107, for example, may include an on-board storage device 70 (FIG. 4), 96(FIG. 5) or an on-chip storage device 82 (FIG. 4), 104 (FIG. 5). In oneembodiment, for example, a first programmable parameter set isidentified as drive 1 parameter set 110, another programmable parameterset is identified as drive 4 parameter set 112, and additionalprogrammable parameter sets are identified as drive N parameter set 114.In another embodiment, the local memory device 107 may include fourprogrammable parameter sets. However, there may be more or lessprogrammable parameter sets in additional embodiments. Each programmableparameter set may include multiple programmable operating parameters.The programmable parameter sets may also be viewed as a plurality ofprogrammable operating parameters that may be arranged in sets accordingto, for example, different environmental conditions for the power drivenwheelchair (e.g., indoor, outdoor, etc.).

With reference to FIG. 7, an exemplary embodiment of the portablestorage medium 115 may include a plurality of storage locations that maystore a security key 116 and a plurality of library parameter sets. Theportable storage medium 115 has the same characteristics and features ofthe portable storage medium 86 (FIG. 4), 106 (FIG. 5) described above.In one embodiment, for example, a first library parameter set isidentified as library 1 parameter set 117, another library parameter setis identified as library 4 parameter set 118, and additional libraryparameter sets are identified as library N parameter set 119. In anotherembodiment, the portable storage medium 115 may include four libraryparameter sets. However, there may be more or less library parametersets in additional embodiments. Each library parameter set may includemultiple programmable operating parameters. The library parameter setsmay also be viewed as a plurality of programmable operating parametersthat may be arranged in sets according to, for example, differentenvironmental conditions for the power driven wheelchair (e.g., indoor,outdoor, etc.). In one embodiment, the same portable storage medium 115may be used effectively when installed directly in a system controlleror when installed in a programmer connected to the same systemcontroller.

With reference to FIG. 8, an exemplary embodiment of a system controller120 may include a power/drive select switch 122, a mode select switch124, a graphic display 126, a joystick control 128, a speed control 130,and a mounting hub 132. This configuration of the system controller 120may be referred to as a multi-purpose joystick (MPJ) model. The MPJmodel may also include a removable memory card slot (not shown) forreceiving a portable storage medium 86 (FIG. 4), such as a removablememory card.

The power/drive select switch 122, for example, may include a threeposition rotary switch. The “on” position, for example, is a centerposition where the power driven wheelchair is powered on. The “driveselect” position is a return-to-center position that advances throughthe available drives (i.e., programmable parameter sets). For example,when the “drive select” position is activated in programming mode, anext programmable parameter set from a group of programmable parametersets stored in the system controller 32 is selected in relation to acurrently-selected programmable parameter set. In one embodiment, theplurality of programmable parameters may include four programmableparameter sets. However, there may be more or less programmableparameter sets in additional embodiments. The “off” position of thepower/drive select switch 122 is, for example, a latching positionopposite the “drive select” position where the power driven wheelchairis powered down.

The mode select switch 103, for example, is a momentary pushbuttonswitch. When the mode select switch 103 is activated, for example, anext mode from a plurality of modes is selected in relation to acurrently-selected mode. The plurality of modes, for example, mayinclude a driving mode, an automated positioning mode associated withpowered seating or powered front rigging, a 4-way switch positioningmode associated with powered seating or powered front rigging, and anenvironmental control unit (ECU) mode. Other embodiments may include anycombination of these modes and additional modes.

The graphic display 126, for example, may include a 128×64 pixeldisplay. A screen on the graphic display 126 may include about five orsix lines of text by about 32 characters, about two large icons (e.g.,64×64 pixels icons), about eight small icons (e.g., 32×32 pixel icons),or various combinations thereof. Of course, larger or smaller icons mayalso be used in various combinations.

The joystick control 128, for example, may include a proportional analogjoystick. The joystick control 128, for example, may be used fordirectional control for menu or icon navigation, setting or modifying aprogrammable parameter, saving a selected programmable parameter value,directional control for driving the power driven wheelchair, positionalcontrol of a selected user support surface, and other selection-typefunctions when directional or positional control is not required. Thejoystick control 128 is an example of a screen navigation control. Thespeed control 130, for example, may include a rotary potentiometer.Turning the speed control 130 between counter-clockwise and clockwiselimits adjusts the maximum speed of the power driven wheelchair inrelation to operation using the joystick control 128. The mounting hub132, for example, may be inserted in a mating receptacle on the powerdriven wheelchair to mount the system controller 32.

With reference to FIG. 9, another exemplary embodiment of a systemcontroller 140 may include a mode select switch 124, a graphic display126, a joystick control 128, a speed control 130, a mounting hub 132, apower/drive select switch 142, and a removable memory card slot 144.This system controller 140 may be referred to as a personalized switchrear-mount (PSR) joystick model or simply a PSR model. Generally, thecomponents of the PSR model have the same functional characteristics asthe components described above for the MPJ model (FIG. 8). The PSR modelprovides an alternate construction of a system controller.

With reference to FIG. 10, still another exemplary embodiment of asystem controller 150 may include a mode select switch 124, a graphicdisplay 126, a joystick control 128, a speed control 130, and apower/drive select switch 142. This system controller 150 may bereferred to as a personalized switch front-mount (PSF) joystick model orsimply a PSF model. A mounting hub (not shown) may also be provided onthe PSF model for mounting the system controller 150. The PSF model mayalso include a removable memory card slot (not shown) for receiving aportable storage medium 86 (FIG. 4), such as a removable memory card.Generally, the components of the PSF model have the same functionalcharacteristics as the components described above for the MPJ model(FIG. 8). The PSF model provides an alternate construction of a systemcontroller.

With reference to FIG. 11, yet another exemplary embodiment of a systemcontroller 160 may include a removable memory card slot 144, an infoswitch 162, a power switch 164, a graphic display 166, an up directionswitch 168, a down direction switch 170, a menu/left direction switch172, a right direction switch 174, a select switch 176, and a saveswitch 178. This system controller 160 may be referred to as a DISPLAYmodel. The DISPLAY model may also include a mounting hub (not shown) formounting the system controller 160. Generally, the removable memory cardslot 144 has the same functional characteristics as described above forthe MPJ model (FIG. 8).

The info switch 162, for example, may include a momentary pushbuttonswitch. Activation of the info switch 162 may cause the controller 160to access and display help information. Certain information from helpinformation file(s) may be provided on the graphic display 166. The helpinformation provided may be related to the content of the display at orabout the time the info switch 162 was activated. For example,information retrieved from help information file(s) may becontext-sensitive with respect to an active screen object, such as acurrent menu or icon selection, a current programmable parameterselection, a current drive selection, a current mode selection, or acurrent error message. This provides information about a specific itemas it is currently being used. The context-sensitive help informationmay: i) explain current selections for operation or support of the powerdriven wheelchair, ii) current settings for programmable parameters,iii) current selection(s) with respect to screen objects (i.e., activescreen object(s)) of the display, and iv) describe an expected resultfrom activation of the selected option. In additional embodiments,retrieval of specific information from the help information file(s) maybe menu-driven, topic-driven, or driven by another suitable means.

The power switch 164, for example, may include a two position toggleswitch with on and off positions. When the power switch 164 is set tothe “on” position the power driven wheelchair is powered on. When thepower switch 164 is switched from the “on” position to the “off”position, for example, the power driven wheelchair may begin apredetermined shutdown sequence. The graphic display 166, for example,is a 160×160 pixel display. A screen on the graphic display 166 mayinclude about twelve lines of text by about 40 characters, about fourlarge icons (e.g., 64×64 pixels icons), about 25 small icons (e.g.,32×32 pixel icons), or various combinations thereof. Of course, largeror smaller icons may also be used in various combinations.

The up, down, menu/left, and right direction switches 168, 170, 172,174, for example, may include momentary pushbutton switches. The up,down, menu/left, and right direction switches 168, 170, 172, 174 may beused for directional control for menu or icon navigation, setting ormodifying a programmable parameter, positional control of a selecteduser support surface, and other selection-type functions whendirectional or positional control is not required. For certain displayscreens, activation of the menu/left direction switch 172 may cause thecontroller 160 to present the previous menu on the graphic display 166.The up, down, menu/left, and right direction switches 168, 170, 172,174, in any combination, are examples of a screen navigation control. Inanother embodiment, the up, down, menu/left, and right directionswitches 168, 170, 172, 174, for example, may also be used fordirectional control for certain power driven wheelchair drivingoperations.

The select switch 176, for example, may include a momentary pushbuttonswitch. The select switch 176 may be used for selection of menu items oricons. The save switch 178, for example, may include a momentarypushbutton switch. The save switch 178 may be used for saving adisplayed value of a selected programmable parameter as the currentvalue for the parameter. The mode select, drive select, and speedcontrol functions described above for the MPJ model (FIG. 7), forexample, may be implemented through the graphic display 166,navigational control using the up, down, menu/left, and right directionswitches 168, 170, 172, 174, and activation of the select or saveswitches 176, 178.

With reference to FIG. 12, an exemplary embodiment of a programmer 180may include a removable memory card slot 144, a graphic display 166, anup direction switch 168, a down direction switch 170, a menu/leftdirection switch 172, a right direction switch 174, a select switch 176,a save switch 178, and a power/info switch 182. Generally, thecomponents of the programmer 180 have the same functionalcharacteristics as the components described above for the DISPLAY modelof the system controller 160 (FIG. 11). However, the programmer 180 maycombine the power and info functions in the power/info switch 182.Notably, the programmer 180 may not require the speed controlfunctionality of the DISPLAY model. The programmer 180 may also notrequire other functionality of the DISPLAY model in relation to drivingthe power driven wheelchair or positioning the user support surfaces.

The power/info switch 182, for example, may include a momentary switch.Pressing and holding the power/info switch 182 for at least apredetermined time (e.g., three seconds) may provide control of togglingpower on and power off functions. For example, if the programmer 180 ispowered off, pressing and holding the power/info switch 182 for at leastthe predetermined time may cause the programmer 180 to be powered on.Similarly, if the programmer 180 is powered on, pressing and holding thepower/info switch 182 for at least the predetermined time may cause theprogrammer 180 to begin a predetermined shutdown sequence. The infofunction may be provided by pressing and releasing the power/info switch182 within a predetermined time (e.g., two seconds). The characteristicsof the info function of the power/info switch 182 are otherwise the sameas those described above for the info switch 162 of the DISPLAY model ofthe system controller 160 (FIG. 11).

With reference to FIG. 13, an exemplary sequence 200 of display screenson a system controller or programmer associated with setting ormodifying an exemplary programmable parameter within a selectedprogrammable parameter set associated with a power driven wheelchairbegins at a first screen 202. The first screen 202 depicts an exemplarymain menu for a programming mode of the power driven wheelchair. Asshown in 202, a currently selected programmable parameter set is namedDRIVE 1. DRIVE 1 is also labeled OUTDOOR which infers that itsprogrammable parameters are set to values suitable for driving the powerdriven wheelchair in an outdoor environment. A SPEED programmableparameter in DRIVE 1 is currently set to 90%. Bold highlightingindicates that the SPEED programmable parameter is currently selected.In other embodiments, use of a pointer or any other suitable form ofhighlighting may be used to indicate the current or active selection inthis menu and subsequent menus or other types of screens. With the SPEEDprogrammable parameter selected, a “select” activation advances thesequence 200 to the second screen 204. The “select” activation, forexample, may be performed by moving a joystick control to the right orby activating a select switch.

The second screen 204 depicts an exemplary set/modify screen for theSPEED programmable parameter. As shown in 204, the current value of theSPEED programmable parameter for drive 1 (i.e., D1) is 90%. A progressbar may provide a graphical representation of the current 90% value. TheMORE and LESS objects indicate that the programmable parameter is a“range” parameter and that the value of the parameter may be selected byactivation of, for example, a joystick control or up or down directionswitches. For example, moving a joystick control on a system controllerforward may be a MORE activation and moving it back may be a LESSactivation. Similarly, pressing an up direction switch on a systemcontroller or programmer may be a MORE activation and pressing a downdirection switch may be a LESS activation. As shown by the boldhighlighting, the MORE object may have been the last control activation.In other embodiments, use of a pointer or any other suitable form ofhighlighting may be used to indicate the last control activation.However, if the LESS object was the last control activation, the LESSobject may be highlighted in bold. For example, after one or more LESSactivations, the third screen 206 may be displayed.

The third screen 206 shows that the current value for the SPEEDprogrammable parameter is now 80%. For example, if the SPEEDprogrammable parameter is adjusted in five percent intervals, thischange from 90% to 80% is based on two LESS activations. Alternatively,if the resolution for adjusting the programmable parameter is twopercent, five LESS activations would produce the ten percent adjustmentshown in the third screen 206. The interval or resolution for adjustmentof a given programmable parameter can be any suitable value and can belinear or non-linear. In one embodiment, neither the LESS nor the MOREobjects are initially highlighted by default. However, the LESS objectis highlighted, for example, in bold and the MORE object is returned tonormal text following a LESS activation. Similarly, for a MOREactivation, the MORE object is highlighted, for example, in bold and theLESS object is returned to normal text. At 206, activation of a saveswitch saves the displayed value (i.e., 80%) for the SPEED programmableparameter in a corresponding storage location associated with theselected programmable parameter set (e.g., D1).

Activation of the save switch may also automatically advance thesequence 200 to the fourth screen 208 which is the main menu for theprogramming mode. In another embodiment, a previous menu activation maybe required to reverse the sequence 200 until the main menu is againdisplayed as shown in the fourth screen 208. For example, moving ajoystick control on a system controller to the left may be interpretedas a previous menu activation. Similarly, pressing a left directionswitch on a system controller or programmer may be interpreted as aprevious menu activation. The fourth screen 208 depicts the exemplarymain menu of the programming mode with the current value of the SPEEDprogrammable parameter for DRIVE 1 now set to 80%.

With reference to FIG. 14, another exemplary sequence 210 of displayscreens on a system controller or programmer associated with setting ormodifying another exemplary programmable parameter within a selectedprogrammable parameter set associated with a power driven wheelchairbegins at a first screen 212. The first screen 212 depicts an exemplarymain menu for a programming mode of the power driven wheelchair. Asshown in 212, a currently selected programmable parameter set is namedDRIVE 1. DRIVE 1 is also labeled OUTDOOR which infers that itsprogrammable parameters are set to values suitable for driving the powerdriven wheelchair in an outdoor environment. Bold highlighting indicatesthat the ADVANCED MENU is currently selected. This may be the defaultselection when the main menu is initially displayed or it may be theresult of one or more down or up activations using a joystick control oran up or down direction switch. In other embodiments, use of a pointeror any other suitable form of highlighting may be used to indicate thecurrent or active selection in this menu and subsequent menus or othertypes of screens. With the ADVANCED MENU selected, a “select” activationadvances the sequence 210 to the second screen 214. The “select”activation, for example, may be performed by moving the joystick controlto the right or by activating a select switch.

The second screen 214 depicts an exemplary ADVANCED MENU. The ADVANCEDMENU, for example, may include five or more menu items in a list. Anindividual menu item may be selected by navigating up or down the listof menu items. The display, however, may not be able to display all ofthe menu items together. As shown in 214, the first four items areinitially displayed on the screen and bold highlighting indicates thatthe first menu item, PERFORMANCE ADJUST, is currently selected. In orderto select the last menu item, five down activations may be required.With the fourth down activation, the screen may begin to scroll down thelist of menu items. After the last menu item selected, for example, thedisplay may continue to scroll to the beginning of the list withadditional down activations. Conversely, if the last menu item isselected, additional down activations may have no effect and upactivations may be required to move up the menu list. Of course, up ordown activations using the joystick control or up and down directionswitches may be used to navigate the list of menu items. For the secondscreen 214, PERFORMANCE ADJUST is selected and a “select” activationadvances the sequence 210 to the third screen 215.

The third screen 215 depicts an exemplary DRIVE SELECT list. The DRIVESELECT list identifies multiple programmable parameter sets forselection of a specific set for which programmable parameters are to beset or modified. As shown in 215, there may be four programmableparameter sets and a currently selected programmable parameter set(i.e., DRIVE 1) may be initially selected by default and highlighted inbold. Up or down activations using the joystick control or up and downdirection switches may be used to navigate the list of menu items. Forthe third screen 215, a “select” activation selects the programmableparameter set associated with the highlighted menu item and advances thesequence 210 to the fourth screen 216.

The fourth screen 216 depicts an exemplary PARAMETER SELECT list ofprogrammable parameters. The PARAMETER SELECT list, for example, mayinclude a plurality of programmable parameters for DRIVE 1 which may beindividually selected by navigating up or down the list. For example,after eleven down activations, the display has scrolled down the list toan INPUT TYPE programmable parameter associated with DRIVE 1 and thefifth screen 218 is displayed. At this point, the INPUT TYPEprogrammable parameter is selected and a “select” activation advancesthe sequence 210 to the sixth screen 220.

The sixth screen 220 depicts an exemplary set/modify screen for theINPUT TYPE programmable parameter. As shown in 220, the current value ofthe INPUT TYPE programmable parameter for DRIVE 1 is MPJ. For example,MPJ may represent an MPJ model system controller. The list of fouroptions (e.g., MPJ, PSR, PSF, and DISP) indicates that programmableparameter is a “choice” parameter and that the value of the parametermay be selected by navigating up or down the list. For example, two downactivations moves the pointer down to the PSF option and a “select”activation advances the sequence 210 to the seventh screen 222. Forexample, PSF may represent a PSF model system controller.

The seventh screen 222 shows that the current value for the INPUT TYPEprogrammable parameter is now PSF. With the current value and theselected option both PSF, for example, a “save” activation saves thecurrent value of the INPUT TYPE programmable parameter for DRIVE 1 in acorresponding storage location. With the current value and the selectedoption both PSF, for example, activation of the save switch may alsoautomatically advance to the eighth screen 224. In another embodiment,one or more previous menu activation may be required to reach the eighthscreen 224. Under the exemplary circumstances described herein, theselect switch and the save switch can be a common multi-function switch,such as moving a joystick control to the right. However, in anotherembodiment, the select and save switches may be separate switches.

The eighth screen 224 depicts the exemplary PARAMETER SELECT list ofprogrammable parameters as displayed in the fourth screen 216. However,at this point, if one were to scroll down to the INPUT TYPE programmableparameter, the current value would be PSF. From 224, a previous menuactivation, for example, may result in display of the ADVANCE MENUscreen 214 again. Likewise, another previous menu activation, forexample, may result in display of the main menu again, as shown in thefirst screen 212.

With reference to FIG. 15, an exemplary programming mode menu hierarchy264 for setting or modifying a programmable parameter associated withoperation of a power driven wheelchair begins with a main menu 266. Asimilar embodiment of the main menu 266 is also depicted in FIG. 13 anddescribed above in more detail. An advanced menu 268 may be selectedfrom the main menu 266. A similar embodiment of the advanced menu 268 isdescribed above in more detail with reference to FIG. 14. Performanceadjust 270 may be selected after from the advanced menu 268. A similarembodiment of the performance adjust 270 is described above in moredetail with reference to FIG. 14.

A standard programs menu 272 may be selected from the advanced menu 268.An SD card menu 274 may also be selected from the advanced menu 254.Additional menus or items, such as a drive pgrm (program) item 276, astore (drive program) to SD card item 278, a read (drive program) fromSD card item 280, a system item 282, a store (system) to SD card item284, and a read (system) from SD card item 286 may be selected withinthe hierarchy of the SD card menu 274. In other embodiments, the SD cardmenu 274 may be referred to as a removable memory card menu or aportable storage medium menu. Additional menus or lists, such as adiagnostics menu 288, a powered seating menu 290, and a calibrationsmenu 292 may also be selected from the advanced menu 268.

With reference to FIG. 16, an exemplary mode select monitor process 300associated with setting or modifying a programmable parameter begins at302 where the process starts. At 304, the process may detect activationof a mode select switch (e.g., 124 (FIG. 8)). In another embodiment, theprocess may periodically check the condition of the mode select switch.If the mode select switch was activated, system programs that arerunning for a current mode, such as a driving mode, may be suspended orended so that a system mode can be selected (306). After a mode isselected, suspended system programs that are compatible with theselected mode may be continued while those that are not compatible maybe ended. If the programming mode is selected in 308, the programmingprocess (see FIG. 17) may be started in 310. If the programming processwas suspended in 306, it may be continued in 310. Next, at 312, the modeselect monitor process is repeated. The various aspects of FIG. 16described above may be automated, semi-automated, or manual and may beimplemented through hardware, software, firmware, or combinationsthereof.

With reference to FIG. 17, an exemplary programming process 320associated with setting or modifying a programmable parameter begins at322 where the process starts. At 324, programming process settings maybe initialized and a main menu may be displayed on a graphic display(e.g., 124 (FIG. 8)). A security check may be performed prior toadvancing from the main menu to prevent unauthorized setting ormodifying of programmable parameters (326). This security check isoptional and not required, particularly in regard to the programmingfunctions. It is described here because in certain applications users,attendants, and technicians may have different privileges with regard tooperation and support of the power driven wheelchair. A security checkfacilitates limiting access to one or more features provided in thepower driven wheelchair. For example, a security check may be used tolimit access to programming function to technicians.

In one embodiment, the security check, for example, may include ahardware or software key associated with insertion of an appropriateportable storage medium (e.g., 86 (FIG. 4)), such as a removable memorycard, in a storage medium interface (e.g., 72 (FIG. 4)), such asremovable memory card slot (e.g., 144 (FIG. 9)). In another embodiment,the security check, for example, may include a hardware or software keyassociated with connection of the programmer (e.g., 60 (FIG. 3)) to thesystem controller (e.g., 32 (FIG. 3)). If the programmer is being used,the security check may include a key status signal transmitted by theprogrammer to the system controller.

If the security check at 328 passes, the programming process may returnto 326 to repeat the security check and also may advance to 330 to startor continue a menu navigation sub-process (see FIG. 18) and to start orcontinue a drive select monitor sub-process (see FIG. 21). At 330, otherprogramming sub-processes may also be started or continued. The securitycheck, for example, may be repeated about every ten milliseconds whilethe programming process is running. In additional embodiments, thesecurity check may be repeated at a different periodic interval.Moreover, the interval between successive security checks may beaperiodic, rather than periodic. Since 326-330 are repeated, after theinitial successful pass through the security check the menu navigationsub-process, drive select monitor sub-process, and any other programmingsub-process may be continued in 330 after additional successful passesthrough the security check.

If the security check does not pass at 328, the programming process mayadvance to 332 to determine if a predetermined timeout period hasexpired. If the timeout period is not expired, the process may return to328 to determine if the security check passed. If the timeout period isexpired at 332, a security error message may be displayed (334) and theprogramming process may be ended (336). The various aspects of FIG. 17described above may be automated, semi-automated, or manual and may beimplemented through hardware, software, firmware, or combinationsthereof.

With reference to FIG. 18, an exemplary menu navigation sub-process 340associated with setting or modifying a programmable parameter begins at342 where the sub-process starts. At 344, the process may detect an upactivation. If an up activation is not detected, the process does notadvance beyond 344. For example, moving a joystick control (e.g., 128(FIG. 8)) forward or pressing an up direction switch (e.g., 168 (FIG.11)) may provide an up activation. If an up activation is detected, themenu item above the current menu item may be selected and highlighted toindicate the newly selected menu item (346). The previously highlightedmenu item may be returned to normal text. Next, at 348, the menunavigation sub-process may be repeated.

At 350, the process may detect a previous menu activation. If a previousmenu activation is not detected, the process does not advance beyond350. For example, moving a joystick control (e.g., 128 (FIG. 8)) to theleft or pressing a menu/left direction switch (e.g., 172 (FIG. 11)) mayprovide an previous menu activation. If a previous menu activation isdetected, the previous menu in a menu hierarchy (e.g., 264 (FIG. 15))may be displayed (352), unless, for example, the current menu is themain menu. Next, at 348, the menu navigation sub-process may be repeatedwith respect to the previous menu.

At 354, the process detects a down activation. If a down activation isnot detected, the process does not advance beyond 354. For example,moving a joystick control (e.g., 128 (FIG. 8)) backward or pressing adown direction switch (e.g., 174 (FIG. 11)) may provide a downactivation. If a down activation is detected, the menu item below thecurrent menu item may be selected and highlighted to indicate the newlyselected menu item (356). The previously highlighted menu item may bereturned to normal text. Next, at 348, the menu navigation sub-processmay be repeated.

At 358, the process detects a select activation. If a select activationis not detected, the process does not advance beyond 358. For example,moving a joystick control (e.g., 128 (FIG. 8)) to the right or pressinga select switch (e.g., 174 (FIG. 11)) may provide a select activation.If a select activation is detected, the menu navigation sub-process maybe ended and a menu item selection handler sub-process (see FIG. 19) maybe started.

In another embodiment, the menu navigation sub-process 340 mayperiodically check the condition of the corresponding componentsassociated with an up activation, previous menu activation, downactivation, and select activation in a loop to determine ifcorresponding activations occur. The various aspects of FIG. 18described above may be automated, semi-automated, or manual and may beimplemented through hardware, software, firmware, or combinationsthereof.

With reference to FIG. 19, an exemplary menu item selection handlersub-process 370 associated with setting or modifying a programmableparameter begins at 372 where the sub-process starts. At 374, if thecurrent menu item selection is a programmable parameter, the sub-processmay advance to 376 to determine whether the programmable parameter is a“range” parameter or a “choice” parameter. A “range” parameter is aprogrammable parameter that may be set or modified to a value within apredetermined range of values (e.g., 204 (FIG. 13)). A “choice”parameter is a programmable parameter that may be set to any valuewithin a list of value choices (e.g., 220 (FIG. 14)). If the selectedprogrammable parameter is a “range” parameter, a set/modify “range”parameter screen may be retrieved (378). Next, a current value for theselected programmable parameter associated with a currently selecteddrive may be retrieved (380). The currently selected drive may be basedon, for example, a default drive selection or activations of thepower/drive select switch (e.g., 122 (FIG. 8)). The currently selecteddrive may also be based on drive selection using a drive select screen(e.g., 215 (FIG. 14)) and corresponding menu navigation (see FIG. 18) toselect the drive. The currently selected drive corresponds to aprogrammable parameter set from a plurality of programmable parameters.At 382, the set/modify parameter screen with the current value for theselected programmable parameter and selected drive may be displayed on agraphic display (e.g., 126 (FIG. 8)). Next, the menu item selectionhandler sub-process may be ended and the set/modify parameter handlersub-process (see FIG. 20) may be started.

At 376, if the selected programmable parameter is a “choice” parameter,a set/modify choice parameter screen may be retrieved (386). Then,values for each item in the list of choices for the selectedprogrammable parameter may be retrieved (388). Next, a current value forthe selected programmable parameter associated with a currently selecteddrive may be retrieved (390). At this point, the process advances to 382and continues as described above.

At 374, if the current menu item selection is not a programmableparameter, a new (i.e., lower level) menu was selected and thesub-process may advance to 392 to identify the new menu. Next, the newmenu may be retrieved (394). At 396, the new menu may be displayed.Next, the menu item selection handler sub-process may be ended and themenu navigation sub-process (see FIG. 18) may be started. The variousaspects of FIG. 19 described above may be automated, semi-automated, ormanual and may be implemented through hardware, software, firmware, orcombinations thereof.

With reference to FIG. 20, an exemplary set/modify parameter handlersub-process 400 associated with setting or modifying a programmableparameter begins at 402 where the sub-process starts. At 404, theprocess may detect an up activation. If an up activation is notdetected, the process does not advance beyond 404. If an up activationis detected, the parameter value choice above the current parametervalue choice may be selected and highlighted to indicate the newlyselected parameter value from a list of parameter value choices (i.e.,when the selected programmable parameter is a “choice” parameter) (406).Alternatively, when the selected programmable parameter is a “range”parameter, if an up activation is detected, the selected parameter valuemay be increased to the next predetermined higher value within the rangeof values for the corresponding programmable parameter (406). For the“range” parameter adjustment, a MORE screen object may be highlighted toindicate the last adjustment made to the selected programmable parameterwas based on an up activation. Next, at 408, the set/modify parameterhandler sub-process may be repeated.

At 410, the process may detect a save activation. If a save activationis not detected, the process does not advance beyond 410. For example,moving a joystick control (e.g., 128 (FIG. 8)) to the right or pressinga save switch (e.g., 178 (FIG. 11)) may provide a save activation. If asave activation is detected, the new parameter value may be stored asthe current parameter value for the selected programmable parameter ofthe currently selected drive (412). At 414, the set/modify parameterdisplay may be updated with the new current parameter value for theselected programmable parameter of the currently selected drive. Next,at 408, the set/modify parameter handler sub-process may be repeated.

At 416, the process may detect a down activation. If a down activationis not detected, the process does not advance beyond 416. If an downactivation is detected, the parameter value choice below the currentparameter value choice may be selected and highlighted to indicate thenewly selected parameter value from the list of parameter value choices(i.e., when the selected programmable parameter is a “choice” parameter)(406). Alternatively, when the selected programmable parameter is a“range” parameter, if a down activation is detected, the selectedparameter value may be decreased to the next predetermined lower valuewithin the range of values for the corresponding programmable parameter(406). For the “range” parameter adjustment, a LESS screen object may behighlighted to indicate the last adjustment made to the selectedprogrammable parameter was based on a down activation. Next, at 408, theset/modify parameter handler sub-process may be repeated.

At 420, the process detects a previous menu activation. If a previousmenu activation is not detected, the process does not advance beyond420. If a previous menu activation is detected, the previous menu in amenu hierarchy (e.g., 264 (FIG. 15)) may be displayed (422), unless, forexample, the current menu is the main menu. Next, at 424, the set/modifyparameter handler sub-process may be ended and a menu navigationsub-process (see FIG. 18) may be started.

In another embodiment, set/modify parameter handler sub-process 400 mayperiodically check the condition of the corresponding componentsassociated with an up activation, save activation, down activation, andprevious menu activation in a loop to determine if correspondingactivations occur. The various aspects of FIG. 20 described above may beautomated, semi-automated, or manual and may be implemented throughhardware, software, firmware, or combinations thereof.

With reference to FIG. 21, an exemplary drive select monitor sub-process430 associated with setting or modifying a programmable parameter beginsat 432 where the sub-process starts. At 434, the sub-process may detecta drive select activation of a power/drive select switch (e.g., FIG. 8,122). In another embodiment, the process may periodically check thecondition of the drive select position of the power/drive select switch.If there is a drive select activation, the sub-process may determine ifthe set/modify parameter handler sub-process is running (436). If theset/modify parameter handler sub-process is not running, the next driveafter the currently selected drive in a predetermined list of drives maybecome the current drive (438). The list of drives corresponds to a listof programmable parameter sets. Generally, the list of drives may beadvanced through in a continuous loop so that the selected driveadvances incrementally from the first drive to the last drive with thefirst drive following the last drive. At 440, the selected driveidentified on the display may be updated to reflect the newly selecteddrive and the sub-process returns to 434. Notably, the drive selectmonitor sub-process may be repeated until the programming process ends.

At 436, if the set/modify parameter handler sub-process is running, thenext drive after the currently selected drive may become the currentdrive (442). Next, a current value for the selected programmableparameter associated with the new current drive may be retrieved (444).At 446, the selected drive identified on the display is updated toreflect the newly selected drive, the current value of the selectedprogrammable parameter on the display may be updated to reflect thecurrent value associated with the newly selected drive, and thesub-process returns to 434. The various aspects of FIG. 21 describedabove may be automated, semi-automated, or manual and may be implementedthrough hardware, software, firmware, or combinations thereof.

With reference to FIG. 22, an exemplary sequence of display screens 500on an apparatus associated with a power driven wheelchair forcommunicating a library parameter set from a portable storage medium toa local storage device associated with the power driven wheelchairbegins at a first screen 502. The library parameter set may also bereferred to as a programmable parameter set. However, to simplify thedescription when the parameter set is located on the portable storagemedium it may be referred to as a library parameter set and when theparameter set is on the local storage device associated with the powerdriven wheelchair it may be referred to as a programmable parameter set.Thus, the library parameter set may be read from the portable storagemedium and saved to the local storage device in storage locations for aprogrammable parameter set.

The display screens 500 may be presented on a display 66 (FIG. 4) of asystem controller 32 (FIG. 4) or on a display 92 (FIG. 5) of aprogrammer 60 (FIG. 5) connected to the system controller. The firstscreen 502 depicts an exemplary main menu for a programming mode of thepower driven wheelchair. As shown in 502, a currently selectedprogrammable parameter set may be identified as DRIVE 1 and may be namedOUTDOOR. The main menu may include three menu items and boldhighlighting may indicate that the third menu item, ADVANCED MENU, iscurrently selected. In other embodiments, use of a pointer or any othersuitable form of highlighting may be used to indicate the current oractive selection in this menu and subsequent menus or other types ofscreens. With the ADVANCED MENU selected, a “select” activation mayadvance the sequence 500 to the second screen 504. A “select”activation, for example, may be provided by moving a joystick control128 (FIG. 8) to the right or by pressing a select switch 176 (FIG. 12).

The second screen 504 depicts an exemplary ADVANCED MENU. As shown in504, the ADVANCED MENU may include four menu items and bold highlightingmay indicate that the third menu item, MEMORY CARD, is currentlyselected. With the MEMORY CARD selected, a “select” activation mayadvance the sequence 500 to the third screen 506.

The third screen 506 depicts an exemplary MEMORY CARD menu. As shown in506, the MEMORY CARD menu may include three menu items and boldhighlighting may indicate that the first menu item, DRIVE PROGRAM, iscurrently selected. With the DRIVE PROGRAM selected, a “select”activation may advance the sequence 500 to the fourth screen 508.

The fourth screen 508 depicts an exemplary DRIVE PROGRAM menu. As shownin 508, the DRIVE PROGRAM menu may include two menu items and boldhighlighting may indicate that the second menu item, READ FROM MEMORYCARD, is currently selected. With READ FROM MEMORY CARD selected, a“select” activation may advance the sequence 500 to the fifth screen510.

The fifth screen 510 depicts a SELECT DESTINATION menu. As shown in 510,the SELECT DESTINATION menu may include four menu items and boldhighlighting may indicate that the first menu item, DRIVE 1, iscurrently selected. With DRIVE 1 selected, a “select” activation mayselect a storage area designated for a programmable parameter set namedDRIVE 1 as the destination location for a library parameter set from theportable storage medium. Additionally, the “select” activation mayadvance the sequence 500 to the sixth screen 512.

The sixth screen 512 depicts an exemplary READ FROM MEMORY CARD screen.As shown in 512, the READ FROM MEMORY CARD screen may include three menuitems and bold highlighting may indicate that the third menu item,START, is currently selected. The first and second menu items mayinclude fields that are used to identify a desired library parameter setto be read. For example, a GROUP menu item may include a [FOLDER NAME]field that may identify a folder on the portable storage medium withinwhich the desired library parameter set is stored. Additionally, a NAMEmenu item may include a [LIBRARY NAME] field that may identify aphysical or logical name (e.g., library 1 parameter set) associated withthe desired library parameter set. The [FOLDER NAME] and [LIBRARY NAME]fields, for example, may be filled by browsing a pull-down list using anavigation control and selecting a desired item. Alternatively, anysuitable technique for filling the [FOLDER NAME] and [LIBRARY NAME]fields may be implemented. Once the [FOLDER NAME] and [LIBRARY NAME]fields are filled, with START selected, a “select” activation willinitiate reading the selected library parameter set from the portablestorage medium at storage locations associated with the [FOLDER NAME]and [LIBRARY NAME] and saving it to the local storage device as aprogrammable parameter set at storage locations associated with theselected destination (i.e., DRIVE 1).

With reference to FIG. 23, an exemplary sequence of display screens 520on an apparatus associated with a power driven wheelchair forcommunicating a group of library parameter sets from a portable storagemedium to a local storage device associated with the power drivenwheelchair begins with the first two screens (502, 504) of FIG. 22. Thethird screen 522 depicts an exemplary MEMORY CARD menu. As shown in 522,bold highlighting may indicate that the second menu item, SYSTEM, iscurrently selected. With SYSTEM selected, a “select” activation mayadvance the sequence 520 to the fourth screen 524.

The fourth screen 524 depicts an exemplary SYSTEM menu. As shown in 524,the SYSTEM menu may include two menu items and bold highlighting mayindicate that the second menu item, READ FROM MEMORY CARD, is currentlyselected. With READ FROM MEMORY CARD selected, a “select” activation mayadvance the sequence 520 to the fifth screen 526.

The fifth screen 526 depicts an exemplary READ FROM MEMORY CARD screen.As shown in 526, the READ FROM MEMORY CARD screen may include two menuitems and bold highlighting may indicate that the second menu item,START, is currently selected. The first menu item may include a fieldthat is used to identify a desired group of library parameter sets to beread. For example, a GROUP menu item may include a [FOLDER NAME] fieldthat may identify a folder on the portable storage medium within whichthe desired group of library parameter sets is stored. The [FOLDER NAME]field, for example, may be filled by browsing a pull-down list using anavigation control and selecting a desired item. Alternatively, anysuitable technique for filling the [FOLDER NAME] field may beimplemented. Once the [FOLDER NAME] field is filled, with STARTselected, a “select” activation will initiate reading the selected groupof library parameter sets from the portable storage medium at storagelocations associated with the [FOLDER NAME] and saving the group to thelocal storage device as programmable parameter sets at storage locationsdesignated for the programmable parameter sets.

With reference to FIG. 24, an exemplary sequence of display screens 530on an apparatus associated with a power driven wheelchair forcommunicating a programmable parameter set from a local storage deviceassociated with the power driven wheelchair to a portable storage mediumbegins with the first three screens (502, 504, 506) of FIG. 22. Thefourth screen 532 depicts an exemplary DRIVE PROGRAM menu. As shown in532, the DRIVE PROGRAM menu may include two menu items and boldhighlighting may indicate that the first menu item, SAVE TO MEMORY CARD,is currently selected. With SAVE TO MEMORY CARD selected, a “select”activation may advance the sequence 530 to the fifth screen 534.

The fifth screen 534 depicts a SELECT SOURCE menu. As shown in 534, theSELECT SOURCE menu may include four menu items and bold highlighting mayindicate that the first menu item, DRIVE 1, is currently selected. WithDRIVE 1 selected, a “select” activation may select a storage areadesignated for a programmable parameter set named DRIVE 1 as the sourcelocation of a programmable parameter set from the local storage device.Additionally, the “select” activation may advance the sequence 530 tothe sixth screen 536.

The sixth screen 536 depicts an exemplary SAVE TO MEMORY CARD screen. Asshown in 536, the SAVE TO MEMORY CARD screen may include three menuitems and bold highlighting may indicate that the third menu item,START, is currently selected. The first and second menu items mayinclude fields that are used to identify the programmable parameter setto be saved as a library parameter set. For example, a GROUP menu itemmay include a [FOLDER NAME] field that may identify a folder on theportable storage medium within which the library parameter set will besaved. Additionally, a NAME menu item may include a [LIBRARY NAME] fieldthat may identify a physical or logical name (e.g., library 1 parameterset) associated with the library parameter set to be saved. The [FOLDERNAME] and [LIBRARY NAME] fields, for example, may be filled by browsinga pull-down list using a navigation control and selecting a desireditem. Alternatively, any suitable technique for filling the [FOLDERNAME] and [LIBRARY NAME] fields may be implemented. Once the [FOLDERNAME] and [LIBRARY NAME] fields are filled, with START selected, a“select” activation will initiate reading the selected programmableparameter set from the local storage device at storage locationsassociated with the selected source (i.e., DRIVE 1) and saving it to theportable storage medium as a library parameter set at storage locationsassociated with the [FOLDER NAME] and [LIBRARY NAME] fields.

With reference to FIG. 25, an exemplary sequence of display screens 540on an apparatus associated with a power driven wheelchair forcommunicating a group of programmable parameter sets from a localstorage device associated with the power driven wheelchair to a portablestorage medium begins with the first two screens (502, 504) of FIG. 22.The third screen 542 depicts an exemplary MEMORY CARD menu. As shown in542, bold highlighting may indicate that the second menu item, SYSTEM,is currently selected. With SYSTEM selected, a “select” activation mayadvance the sequence 540 to the fourth screen 544.

The fourth screen 544 depicts an exemplary SYSTEM menu. As shown in 544,the SYSTEM menu may include two menu items and bold highlighting mayindicate that the first menu item, SAVE TO MEMORY CARD, is currentlyselected. With SAVE TO MEMORY CARD selected, a “select” activation mayadvance the sequence 540 to the fifth screen 546.

The fifth screen 546 depicts an exemplary SAVE TO MEMORY CARD screen. Asshown in 546, the SAVE TO MEMORY CARD screen may include two menu itemsand bold highlighting may indicate that the second menu item, START, iscurrently selected. The first menu item may include a field that is usedto identify where a group of library parameter sets are to be saved. Forexample, a GROUP menu item may include a [FOLDER NAME] field that mayidentify a folder on the portable storage medium within which the groupof programmable parameter sets are to be saved. The [FOLDER NAME] field,for example, may be filled by browsing a pull-down list using anavigation control and selecting a desired item. Alternatively, anysuitable technique for filling the [FOLDER NAME] field may beimplemented. Once the [FOLDER NAME] field is filled, with STARTselected, a “select” activation will initiate reading a group ofprogrammable parameter sets from the local storage device at storagelocations designated for programmable parameter sets and saving thegroup to the portable storage medium as library parameter sets atstorage locations associated with the [FOLDER NAME].

With reference to FIGS. 22 and 24, similar exemplary sequences ofdisplay screens on an apparatus associated with a power drivenwheelchair may be associated with selection of the third menu item,SEATING CONTROL, in the MEMORY CARD menu 506. With selection of SEATINGCONTROL, the parameters being read from the portable storage medium orsaved to the portable storage medium may be associated with control ofpowered seating functions or powered front rigging functions.Accordingly, with selection of DRIVE PROGRAM, the parameters being readfrom the portable storage medium or saved to the portable storage mediummay be associated with control of powered driving functions and othernon-seating control functions. However, in another embodiment,parameters for powered driving functions, powered seating functions, andpowered front rigging functions may be included when the DRIVE PROGRAMis selected.

With reference to FIG. 26, a block diagram 600 depicts an apparatus 602associated with a power driven wheelchair 604 for setting or modifying aprogrammable parameter. As shown, the apparatus 602 may include a userinterface device 606 and a first storage device 608. The user interfacedevice may be associated with the power driven wheelchair 604 and may beadapted to operate in a programming mode. The first storage device 608may be in operative communication with the user interface device 606. Atleast a portion of the first storage device 608 may be designated forstorage of a programmable operating parameter 610. The programmableoperating parameter 610 may be associated with operation of the powerdriven wheelchair 604. The user interface device 606 may be used toselect the programmable operating parameter 610, select a value for theprogrammable operating parameter 610, and save the selected value forthe programmable operating parameter 610 in the portion of the firststorage device 608.

In one embodiment, the user interface device 606 may be separate fromthe power driven wheelchair 604, like the programmer 60 (FIG. 5)described above. In another embodiment, as shown by the dotted line, theuser interface device 606 may be part of the power driven wheelchair604, like the system controller 32 (FIG. 4) described above.Accordingly, in one embodiment, the user interface device 606 and thefirst storage device 608 may form at least a portion of a systemcontroller 32 (FIG. 4) associated with the power driven wheelchair 604.In this embodiment, at least one of an on-board storage device 70 (FIG.4) and an on-chip storage device 82 (FIG. 4) may form at least a portionof the first storage device 608.

In another embodiment, the user interface device 606 may form at least aportion of a programmer 60 (FIG. 5) associated with the power drivenwheelchair 604 and the first storage device 608 may form at least aportion of a system controller 32 (FIG. 4) associated with the powerdriven wheelchair 604. In this embodiment, the programmer may be inoperative communication with the system controller. Additionally, atleast one of an on-board storage device 70 (FIG. 4) and an on-chipstorage device 82 (FIG. 4) may form at least a portion of the firststorage device 608. The various aspects of FIG. 26 described above maybe automated, semi-automated, or manual and may be implemented throughhardware, software, firmware, or combinations thereof.

With reference to FIG. 27, a process 620 associated with a power drivenwheelchair for setting or modifying a programmable parameter may beginat 622. At 624, a user interface device associated with a power drivenwheelchair may be operated in a programming mode. Next, a programmableoperating parameter associated with operation of the power drivenwheelchair may be selected using the user interface device (626). At628, a value for the programmable operating parameter may be selectedusing the user interface device. Next, the selected value for theprogrammable operating parameter may be saved in a portion of a storagedevice associated with the power driven wheelchair using the userinterface device (630). From 630, the selecting and saving in 626, 628,and 630, respectively, may be repeated.

In another embodiment, the user interface device and the storage devicemay form at least a portion of a system controller 32 (FIG. 4)associated with the power driven wheelchair. In still anotherembodiment, the user interface device may form at least a portion of aprogrammer 60 (FIG. 5) associated with the power driven wheelchair andthe storage device may form at least a portion of a system controllerassociated with the power driven wheelchair. In this embodiment, theprogrammer may be in operative communication with the system controller.In yet another embodiment, the programmable operating parameter may be arange parameter with selectable parameter values within a range definedby a lower parameter limit and an upper parameter limit. In thisembodiment, the selectable parameter values for the range parameter arefurther defined by predetermined increments between a next higherparameter value or a next lower parameter value for a currently selectedparameter value. In still another embodiment, the programmable operatingparameter may be a choice parameter with a plurality of selectableparameter values. The various aspects of FIG. 27 described above may beautomated, semi-automated, or manual and may be implemented throughhardware, software, firmware, or combinations thereof.

With reference to FIG. 28, a block diagram 640 depicts an apparatus 642associated with a power driven wheelchair 644 for communicating aprogrammable parameter set. As shown, the apparatus 642 may include auser interface device 646, a portable storage medium 648, and a localstorage device 650. The user interface device 646 may be associated withthe power driven wheelchair 644 and may be adapted to operate in aprogramming mode. The portable storage medium 648 may be in operativecommunication with the user interface device 646 with at least a portion652 designated for storage of one or more programmable parameter sets654 associated with operation of the power driven wheelchair 644. Thelocal storage device 650 may be in operative communication with the userinterface device 646 with at least a portion 656 designated for storageof one or more programmable parameter sets 658 associated with operationof the power driven wheelchair 644. The user interface device 646 may beused to select one or more programmable parameter sets 654 from theportable storage medium 648 and save said selected programmableparameter sets 654 to the local storage device 650 or vice versa.

In another embodiment, the user interface device 646 and the localstorage device 650 may form at least a portion of a system controller 32(FIG. 4) associated with the power driven wheelchair 644. The systemcontroller 32 (FIG. 4) may include a storage medium interface 72 (FIG.4) adapted to receive the portable storage medium 648 and facilitateoperative communication between the user interface device 646 and theportable storage medium 648.

In still another embodiment, the user interface device 646 may form atleast a portion of a programmer 60 (FIG. 5) associated with the powerdriven wheelchair 644 and the local storage device 650 may form at leasta portion of a system controller 32 (FIG. 4) associated with the powerdriven wheelchair 644. The programmer 60 (FIG. 5) may be in operativecommunication with the system controller 32 (FIG. 4). The systemcontroller 32 (FIG. 4) may include a storage medium interface 72 (FIG.4) adapted to receive the portable storage medium 648 and facilitateoperative communication between the user interface device 646 and theportable storage medium 648.

In yet another embodiment, the user interface device 646 may form atleast a portion of a programmer 60 (FIG. 5) associated with the powerdriven wheelchair 644 and the local storage device 650 may form at leasta portion of a system controller 32 (FIG. 4) associated with the powerdriven wheelchair 644. The programmer 60 (FIG. 5) may be in operativecommunication with the system controller 32 (FIG. 4). The programmer 60(FIG. 5) may include a storage medium interface 98 (FIG. 5) adapted toreceive the portable storage medium 648 and facilitate operativecommunication between the user interface device 646 and the portablestorage medium 648. The various aspects of FIG. 28 described above maybe automated, semi-automated, or manual and may be implemented throughhardware, software, firmware, or combinations thereof.

With reference to FIG. 29, a process 670 associated with a power drivenwheelchair for communicating a programmable parameter set may start at672. At 674, a user interface device associated with a power drivenwheelchair may be operated in a programming mode. Next, at least oneprogrammable parameter set associated with the power driven wheelchairmay be selected using the user interface device (676). At 678, eachselected programmable parameter set may be communicated from a portablestorage medium associated with the power driven wheelchair to a localstorage device associated with the power driven wheelchair or vice versausing the user interface device. In this embodiment, the portablestorage device may include at least a portion designated for storage ofone or more programmable parameter sets and the local storage device mayinclude at least a portion designated for storage of one or moreprogrammable parameter sets. From 678, the selecting and communicatingin 676 and 678, respectively, may be repeated.

In another embodiment, the user interface device and the local storagedevice may form at least a portion of a system controller 32 (FIG. 4)associated with the power driven wheelchair. In this embodiment, thesystem controller 32 (FIG. 4) may include a storage medium interface 72(FIG. 4) adapted to receive the portable storage medium and facilitateoperative communication between the user interface device and theportable storage medium.

In still another embodiment, the user interface device may form at leasta portion of a programmer 60 (FIG. 5) associated with the power drivenwheelchair and the local storage device may form at least a portion of asystem controller 32 (FIG. 4) associated with the power drivenwheelchair. In this embodiment, the programmer 60 (FIG. 5) may be inoperative communication with the system controller 32 (FIG. 4). Thesystem controller 32 (FIG. 4) may include a storage medium interface 72(FIG. 4) adapted to receive the portable storage medium and facilitateoperative communication between the user interface device and theportable storage medium.

In yet another embodiment, the user interface device may form at least aportion of a programmer 60 (FIG. 5) associated with the power drivenwheelchair and the local storage device may form at least a portion of asystem controller 32 (FIG. 4) associated with the power drivenwheelchair. In this embodiment, the programmer 60 (FIG. 5) may be inoperative communication with the system controller 32 (FIG. 4). Theprogrammer 60 (FIG. 5) may include a storage medium interface 98 (FIG.5) adapted to receive the portable storage medium and facilitateoperative communication between the user interface device and theportable storage medium.

In another embodiment, the programmable parameter sets may includeprogrammable operating parameters associated with driving the powerdriven wheelchair. In another embodiment, the programmable parametersets may include programmable operating parameters associated withoperating powered seating for the power driven wheelchair. In stillanother embodiment, the programmable parameter sets may includeprogrammable operating parameters associated with operating poweredfront rigging for the power driven wheelchair.

In yet another embodiment, the selecting in 676 may include selectingall programmable parameter sets stored on the local storage device andthe communicating in 678 may include communicating said selectedprogrammable parameter sets from the local storage device to theportable storage medium. In another embodiment, the selecting in 676 mayinclude selecting all programmable parameter sets stored within a selectfolder on the portable storage medium and the communicating in 678 mayinclude communicating said selected programmable parameter sets from theportable storage medium to the local storage device. The various aspectsof FIG. 29 described above may be automated, semi-automated, or manualand may be implemented through hardware, software, firmware, orcombinations thereof.

While the invention is described herein in conjunction with one or moreexemplary embodiments, it is evident that many alternatives,modifications, and variations will be apparent to those skilled in theart. Accordingly, exemplary embodiments in the preceding description areintended to be illustrative, rather than limiting, of the spirit andscope of the invention. More specifically, it is intended that theinvention embrace all alternatives, modifications, and variations of theexemplary embodiments described herein that fall within the spirit andscope of the appended claims or the equivalents thereof. Any element ina claim that does not explicitly state “means for” performing aspecified function, or “step for” performing a specific function, is notto be interpreted as a “means” or “step” clause as specified in 35U.S.C. § 112, ¶ 6. In particular, the use of “step of” in the claimsherein is not intended to invoke the provisions of 35 U.S.C. § 112, ¶ 6.

We claim:
 1. An apparatus associated with a power driven wheelchair,comprising: a controller of the power driven wheelchair; and a portablestorage medium interface adapted to facilitate operative communicationbetween the controller and a portable storage medium, wherein theportable storage medium interface comprises a wireless interface;wherein information from the portable storage medium is communicated tothe controller or vice versa via the portable storage medium interface.2. The apparatus of claim 1, wherein the wireless interface comprises an802.11 communication link.
 3. The apparatus of claim 1, wherein thewireless interface comprises an Ethernet transceiver.
 4. The apparatusof claim 1, further comprising: a local storage device in operativecommunication with the controller, wherein at least a portion of thelocal storage device is designated for storage of information associatedwith operation of the power driven wheelchair; and wherein informationassociated with operation of the power driven wheelchair is communicatedfrom the portable storage medium to the local storage device or viceversa.
 5. The apparatus of claim 4, further comprising: a user interfacedevice; wherein communication of information between the portablestorage medium and the local storage device is in response to aselection by a user via the user interface device.
 6. The apparatus ofclaim 1, wherein the portable storage medium comprises a portablecomputer.
 7. The apparatus of claim 1, wherein the portable storagemedium comprises a mobile telephone.
 8. An apparatus associated with apower driven wheelchair, comprising: a controller of the power drivenwheelchair; and a programmer interface adapted to facilitate operativecommunication between the controller and a programmer, wherein theprogrammer interface comprises a wireless interface; wherein informationfrom the programmer is communicated to the controller or vice versa viathe programmer interface.
 9. The apparatus of claim 8, wherein thewireless interface comprises an 802.11 communication link.
 10. Theapparatus of claim 8, wherein the wireless interface comprises anEthernet transceiver.
 11. The apparatus of claim 8, wherein the wirelessinterface comprises a network connection.
 12. The apparatus of claim 8,wherein the programmer comprises a user interface configured for settingor modifying a programmable parameter of the power driven wheelchair.13. The apparatus of claim 12, further comprising: a local storagedevice in operative communication with the controller, wherein at leasta portion of the local storage device is designated for storage of theprogrammable parameter.
 14. The apparatus of claim 8, furthercomprising: a portable storage medium interface adapted to facilitateoperative communication between the controller and a portable storagemedium; wherein the programmer comprises a user interface configured forcommunicating information from the portable storage medium to thecontroller or vice versa via the portable storage medium interface. 15.A method associated with a power driven wheelchair, comprising:providing a controller of the power driven wheelchair; providing aninterface adapted to facilitate operative communication between thecontroller and a portable storage medium, wherein the interfacecomprises a wireless interface; and communicating information from theportable storage medium to the controller or vice versa via theinterface.
 16. The method of claim 15, wherein the interface comprises aportable storage medium interface.
 17. The method of claim 15, whereinthe interface comprises a programmer interface.
 18. The method of claim15, further comprising setting or modifying a programmable parameter ofthe power driven wheelchair via the interface.
 19. The method of claim15, further comprising establishing operative communication between theportable storage medium and the controller via an 802.11 communicationlink.
 20. The method of claim 15, wherein the portable storage mediumcomprises a portable computer or a mobile telephone.
 21. The apparatusof claim 1, further comprising a user interface device associated withthe wireless interface, wherein communication of information between theportable storage medium and the controller is via the wirelessinterface.
 22. The apparatus of claim 1 wherein the wireless interfacecomprises a Bluetooth transceiver.
 23. The apparatus of claim 1 whereinthe wireless interface comprises a radio frequency transceiver.
 24. Theapparatus of claim 8 wherein the wireless interface comprises aBluetooth transceiver.
 25. The apparatus of claim 8 wherein the wirelessinterface comprises a radio frequency transceiver.
 26. The apparatus ofclaim 8, further comprising a user interface device associated with thewireless interface, wherein communication of information between theprogrammer and the controller is via the wireless interface.
 27. Themethod of claim 15 wherein communicating information comprises using aBluetooth connection.
 28. The method of claim 15 wherein communicatinginformation comprises using a radio frequency connection.
 29. The methodof claim 15, further comprising providing a user interface associatedwith the wireless interface, wherein communication of informationbetween the portable storage medium and the controller is via thewireless interface.